Skip to content

Hide the Guardex lock registry from repo change rows#281

Merged
NagyVikt merged 2 commits intomainfrom
agent/codex/vscode-idle-session-decorations-2026-04-22-11-05
Apr 22, 2026
Merged

Hide the Guardex lock registry from repo change rows#281
NagyVikt merged 2 commits intomainfrom
agent/codex/vscode-idle-session-decorations-2026-04-22-11-05

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by scripts/agent-branch-finish.sh (PR flow).

NagyVikt added 2 commits April 22, 2026 11:09
Synthetic gitguardex-agent://<sanitized-branch> URIs let the Active Agents view decorate session rows without pointing at workspace files. The refresh path now invalidates both tree data and session decorations, and the focused tests cover URI assignment plus the 10 minute and 30 minute idle thresholds.

Constraint: Session rows are not backed by real files, so the decoration key must be synthetic and branch-stable
Constraint: Working rows must keep their existing styling
Rejected: Reuse workspace file URIs for session rows | would couple session decoration to unrelated files
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep vscode/guardex-active-agents/extension.js and templates/vscode/guardex-active-agents/extension.js mirrored when session-row UI changes
Tested: node --test test/vscode-active-agents-session-state.test.js; openspec validate agent-codex-vscode-tree-lock-decorations-2026-04-22-10-55 --type change --strict
Not-tested: npm test hangs in test/install.test.js while autofinish flows are spawned
The active-agents session-schema tests on current main already expect .omx/state/agent-file-locks.json to stay out of the CHANGES section. Filtering that path in the runtime and template schema keeps the existing lock-registry rows green without changing the idle session decoration behavior.

Constraint: The lock registry is Guardex metadata, not a user edit, so showing it in repo change rows creates noisy false positives
Rejected: Skip the existing lock-registry assertions | would leave the focused extension test file red on current main
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep metadata files out of repo-root change lists unless the companion explicitly needs to surface them
Tested: node --test test/vscode-active-agents-session-state.test.js
Not-tested: npm test still hangs in test/install.test.js while autofinish flows are spawned
@NagyVikt NagyVikt merged commit 8a68593 into main Apr 22, 2026
1 check passed
@NagyVikt NagyVikt deleted the agent/codex/vscode-idle-session-decorations-2026-04-22-11-05 branch April 22, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant